Assessor Resource

ICTPRG419
Analyse software requirements

Assessment tool

Version 1.0
Issue Date: May 2024


This unit describes the skills and knowledge required to research and analyse client requirements, produce a range of options, and create a software-requirements document.

It applies to individuals in a range of work environments who are required to perform an analysis role in formulating software requirements. They may work as database or computer developers, business analysts, or project managers.

No licensing, legislative or certification requirements apply to this unit at the time of publication.

You may want to include more information here about the target group and the purpose of the assessments (eg formative, summative, recognition)


Evidence Required

List the assessment methods to be used and the context and resources required for assessment. Copy and paste the relevant sections from the evidence guide below and then re-write these in plain English.

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Gather and confirm client requirements

1.1 Confirm the requirements, and the scope, of the project with the client

1.2 Gather information regarding requirements via sources of information and business processes

1.3 Analyse client requirements, to determine the project scope and the problem context or opportunity faced by the business

1.4 Document the client requirements, project’s scope, related problems, and sources of information

2. Analyse the functional and related non-functional requirements

2.1 Map business processes using modelling tools such as unified modelling language (UML)

2.2 Determine the opportunities for business process efficiencies

2.3 Document functional, and related non-functional, processes

3. Analyse the feasibility of a project

3.1 Analyse the technical feasibility of the project

3.2 Analyse the operational feasibility of the project

3.3 Determine the budget and schedule feasibility of the project

3.4 Examine how the project will fit within the organisation

4. Develop high-level system solutions

4.1 Develop and document feasible solutions for client requirements

4.2 Explore and document the feasibility of each solution

4.3 Examine alternatives against project constraints

4.4 Document assumptions, dependencies and required resources

4.5 Produce a project risk analysis

4.6 Document future requirements

5. Prepare and publish the software-requirements documentation

5.1 Develop the software-requirements document

5.2 Submit the software-requirements report to the appropriate person for project approval

Evidence of the ability to:

Analyse client requirements to create a software requirements document, including:

gathering, confirming and documenting client requirements

analysing functional and related non-functional requirements, and project feasibility

developing high-level system solutions

submitting documents for approval.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

identify the client business domain

describe content features, such as clarity and readability

summarise the system's current functions

explain document design and usability

explain the functions and features, of templates and style guides

summarise instructional design principles

describe the role of stakeholders and the degree of stakeholder involvement

explain two or more current industry systems development methodologies.

Gather evidence to demonstrate consistent performance in conditions that are safe and replicate the workplace. Noise levels, production flow, interruptions and time variances must be typical of those experienced in the programming and software development industry, and include access to:

documentation regarding client and functionality requirements

word processing software

modelling software currently used in industry.

Assessors must satisfy NVR/AQTF assessor requirements.

Submission Requirements

List each assessment task's title, type (eg project, observation/demonstration, essay, assingnment, checklist) and due date here

Assessment task 1: [title]      Due date:

(add new lines for each of the assessment tasks)

Assessment Tasks

Copy and paste from the following data to produce each assessment task. Write these in plain English and spell out how, when and where the task is to be carried out, under what conditions, and what resources are needed. Include guidelines about how well the candidate has to perform a task for it to be judged satisfactory.

ELEMENT

PERFORMANCE CRITERIA

Elements describe the essential outcomes.

Performance criteria describe the performance needed to demonstrate achievement of the element.

1. Gather and confirm client requirements

1.1 Confirm the requirements, and the scope, of the project with the client

1.2 Gather information regarding requirements via sources of information and business processes

1.3 Analyse client requirements, to determine the project scope and the problem context or opportunity faced by the business

1.4 Document the client requirements, project’s scope, related problems, and sources of information

2. Analyse the functional and related non-functional requirements

2.1 Map business processes using modelling tools such as unified modelling language (UML)

2.2 Determine the opportunities for business process efficiencies

2.3 Document functional, and related non-functional, processes

3. Analyse the feasibility of a project

3.1 Analyse the technical feasibility of the project

3.2 Analyse the operational feasibility of the project

3.3 Determine the budget and schedule feasibility of the project

3.4 Examine how the project will fit within the organisation

4. Develop high-level system solutions

4.1 Develop and document feasible solutions for client requirements

4.2 Explore and document the feasibility of each solution

4.3 Examine alternatives against project constraints

4.4 Document assumptions, dependencies and required resources

4.5 Produce a project risk analysis

4.6 Document future requirements

5. Prepare and publish the software-requirements documentation

5.1 Develop the software-requirements document

5.2 Submit the software-requirements report to the appropriate person for project approval

Evidence of the ability to:

Analyse client requirements to create a software requirements document, including:

gathering, confirming and documenting client requirements

analysing functional and related non-functional requirements, and project feasibility

developing high-level system solutions

submitting documents for approval.

Note: If a specific volume or frequency is not stated, then evidence must be provided at least once.

To complete the unit requirements safely and effectively, the individual must:

identify the client business domain

describe content features, such as clarity and readability

summarise the system's current functions

explain document design and usability

explain the functions and features, of templates and style guides

summarise instructional design principles

describe the role of stakeholders and the degree of stakeholder involvement

explain two or more current industry systems development methodologies.

Gather evidence to demonstrate consistent performance in conditions that are safe and replicate the workplace. Noise levels, production flow, interruptions and time variances must be typical of those experienced in the programming and software development industry, and include access to:

documentation regarding client and functionality requirements

word processing software

modelling software currently used in industry.

Assessors must satisfy NVR/AQTF assessor requirements.
Copy and paste from the following performance criteria to create an observation checklist for each task. When you have finished writing your assessment tool every one of these must have been addressed, preferably several times in a variety of contexts. To ensure this occurs download the assessment matrix for the unit; enter each assessment task as a column header and place check marks against each performance criteria that task addresses.

Observation Checklist

Tasks to be observed according to workplace/college/TAFE policy and procedures, relevant legislation and Codes of Practice Yes No Comments/feedback
Confirm the requirements, and the scope, of the project with the client 
Gather information regarding requirements via sources of information and business processes 
Analyse client requirements, to determine the project scope and the problem context or opportunity faced by the business 
Document the client requirements, project’s scope, related problems, and sources of information 
Map business processes using modelling tools such as unified modelling language (UML) 
Determine the opportunities for business process efficiencies 
Document functional, and related non-functional, processes 
Analyse the technical feasibility of the project 
Analyse the operational feasibility of the project 
Determine the budget and schedule feasibility of the project 
Examine how the project will fit within the organisation 
Develop and document feasible solutions for client requirements 
Explore and document the feasibility of each solution 
Examine alternatives against project constraints 
Document assumptions, dependencies and required resources 
Produce a project risk analysis 
Document future requirements 
Develop the software-requirements document 
Submit the software-requirements report to the appropriate person for project approval 

Forms

Assessment Cover Sheet

ICTPRG419 - Analyse software requirements
Assessment task 1: [title]

Student name:

Student ID:

I declare that the assessment tasks submitted for this unit are my own work.

Student signature:

Result: Competent Not yet competent

Feedback to student

 

 

 

 

 

 

 

 

Assessor name:

Signature:

Date:

Assessment Record Sheet

ICTPRG419 - Analyse software requirements

Student name:

Student ID:

Assessment task 1: [title] Result: Competent Not yet competent

(add lines for each task)

Feedback to student:

 

 

 

 

 

 

 

 

Overall assessment result: Competent Not yet competent

Assessor name:

Signature:

Date:

Student signature:

Date: